Click any tag below to further narrow down your results
Links
@undefinedKi on X
This is a twelve-step walkthrough for setting up Claude once so it remembers your context, reuses your methods, and works across your tools without re-explaining everything each session. It draws on Anthropic's release notes and says which features live in the chat app versus Cowork.
- Start with memory and projects, since skills, connectors, and scheduled tasks all read from them. Projects keep separate instructions, files, and memory per recurring job.
- Save repeated methods as skills, written after you've done the task manually twice, and include when to use them, steps, output format, and what never to do.
- Connect tools like Gmail, Google Calendar, Drive, Notion, Slack, and GitHub in one sitting, and run scheduled tasks read-only at first, checking the first run before trusting it.
The author argues that treating prompts as disposable is wasteful—instead, build modular "skills" (organized folders with instructions and scripts) that you improve over time and chain together. He breaks down 17 tactics from Anthropic engineers into 6 layers, showing how to structure workflows so improvements compound across tasks rather than starting from scratch each time.
- The author rebuilt a 600-line SEO prompt into six modular skill files (research, audit, metadata, internal links, GSC monitoring, title scoring), and improving one now improves every workflow that uses it.
- The core shift is from one-off prompting to building reusable "skills"—folders with a SKILL.md file, scripts, and references—that Claude runs identically every time and that get refined after each failure.
- Anthropic engineers' 17 tactics get grouped into 6 layers, with the top priority being: stop writing custom prompts for repetitive tasks and instead build slash-command-invoked skills.
- The lasting value comes from the infrastructure built on top of Claude, not from any single prompt, which evaporates once the session ends.